Minutes, IBIS Quality Task Group 03 July 2018 11:00-12:00 EST (08:00-09:00 PST) ROLL CALL eASIC: David Banas Ericsson: Anders Ekholm Intel: Michael Mirmak Eugene Lim IO Methodology: Lance Wang Mentor, a Siemens Business Arpad Muranyi Signal Integrity Software: * Mike LaBonte Teraspeed Labs: * Bob Ross Visteon: Preetesh Rathod Everyone in attendance marked by * NOTE: "AR" = Action Required. -----------------------MINUTES --------------------------- Mike LaBonte conducted the meeting. Call for IBIS related patent disclosures: - None Call for opens: - None Review of previous meeting minutes: - Bob: It was sent to 1ibis@freelists.org. Bob Ross moved to approve the June 26 minutes. Mike LaBonte seconded. Without objection the minutes were approved. ARs: - Mike LaBonte to complete BIRD appendix for parser contract. - This needs to be broken into smaller ARs, for BIRD189.7. New IBISCHK bugs: - No discussion. IBISCHK7 parser development: - Bob: My document from last week was about rails. - It is about [Interconnect Model] only. - The rail relaxation rule means nothing needs to be checked. - A pin name in one [Interconnect Model] can be connected to a terminal that is a signal name in another [Interconnect Model]. - For example, any given *_I/O Terminal_type cannot be on more than one line in an [Interconnect Model]. - Two [Interconnect Model]s can attach to the same terminal, however. - Mike showed BIRD189.7. - Mike: If two [Interconnect Model]s have the same signal names for Pin_Rail and Buffer_Rail, are they shorted at both points, and therefore in parallel? - Bob: VSS might be a single node in some models. - Other models in a [Interconnect Model Group] might use VSS as a reference terminal. - We do not determine the purpose of a second [Interconnect Model] terminal to be as a reference. - *_Rail terminals truly are shorted when assigned to the same name, even when not in the same [Interconnect Model]? - Bob: Correct. - They can't be in the same [Interconnect Model] though. They can't overlap. - Mike: We are using overlap to mean effectively connected together, even though by different means? - Bob: Yes. - Mike: Software producing these models might run into trouble with that rule. - Mike: We should make a a list of the error messages to be produced. - Will any checks be at [Interconnect Model Group] level? - Bob: The only only [Interconnect Model Group] check is that we don't duplicate the same non-aggressor I/O path. - Mike: I can take the AR to start a check list with messages. - Bob: We need to specify checking for .ims files. AR: Bob Ross to write rules for Table 41. AR: Bob Ross to write description of .ims file header checking. AR: Mike LaBonte to write list of syntax check messages - Bob Ross moved to adjourn. Mike LaBonte seconded. Without objection the meeting ended. Meeting ended: 12:02 ET Next meeting July 10, 2018